Package | hl7.fhir.us.exchange-routing |
Type | CapabilityStatement |
Id | Id |
FHIR Version | R4 |
Source | http://hl7.org/fhir/us/exchange-routing/https://build.fhir.org/ig/HL7/fhir-exchange-routing-ig/CapabilityStatement-exchange-routing-intermediary.html |
Url | http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-intermediary |
Version | 1.0.0 |
Status | active |
Date | 2022-05-17T00:00:00-05:00 |
Name | ExchangeRoutingIntermediaryCapabilityStatement |
Title | Exchange Routing Intermediary Capability Statement |
Experimental | False |
Realm | us |
Authority | hl7 |
Description | This CapabilityStatement describes the expected capabilities of an intermediary server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide. |
Kind | requirements |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
This CapabilityStatement describes the expected capabilities of an intermediary server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.
Mode | SERVER |
Description | When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server SHALL pass FHIR resources returned by the destination server to the originator unchanged. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format. When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server, the intermediary server SHOULD: 1. Support the XML source format. |
Transaction | |
System History | |
System Search |
Resource Type | Profile | Read | Search | Update | Create |
---|
{
"resourceType" : "CapabilityStatement",
"id" : "exchange-routing-intermediary",
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>ExchangeRoutingIntermediaryCapabilityStatement</h2><div><p>This CapabilityStatement describes the expected capabilities of an intermediary server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.</p>\n</div><table><tr><td>Mode</td><td>SERVER</td></tr><tr><td>Description</td><td><div><p>When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server <strong>SHALL</strong> pass FHIR resources returned by the destination server to the originator unchanged. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format.\nWhen participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server, the intermediary server <strong>SHOULD</strong>: 1. Support the XML source format.</p>\n</div></td></tr><tr><td>Transaction</td><td></td></tr><tr><td>System History</td><td></td></tr><tr><td>System Search</td><td></td></tr></table><table><tr><th><b>Resource Type</b></th><th><b>Profile</b></th><th><b title=\"GET a resource (read interaction)\">Read</b></th><th><b title=\"GET all set of resources of the type (search interaction)\">Search</b></th><th><b title=\"PUT a new resource version (update interaction)\">Update</b></th><th><b title=\"POST a new resource (create interaction)\">Create</b></th></tr></table></div>"
},
"url" : "http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-intermediary",
"version" : "1.0.0",
"name" : "ExchangeRoutingIntermediaryCapabilityStatement",
"title" : "Exchange Routing Intermediary Capability Statement",
"status" : "active",
"experimental" : false,
"date" : "2022-05-17T00:00:00-05:00",
"publisher" : "HL7 International - FHIR Infrastructure",
"contact" : [
{
"name" : "HL7 International - FHIR Infrastructure",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/fiwg"
}
]
},
{
"name" : "Frank McKinney",
"telecom" : [
{
"system" : "email",
"value" : "frank.mckinney@pocp.com"
}
]
}
],
"description" : "This CapabilityStatement describes the expected capabilities of an intermediary server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "urn:iso:std:iso:3166",
"code" : "US",
"display" : "United States of America"
}
]
}
],
"kind" : "requirements",
"fhirVersion" : "4.0.1",
"format" : [
"xml",
"json"
],
"patchFormat" : [
"application/json-patch+json"
],
"implementationGuide" : [
"http://hl7.org/fhir/us/exchange-routing/ImplementationGuide/exchange-routing"
],
"rest" : [
{
"mode" : "server",
"documentation" : "When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server **SHALL** pass FHIR resources returned by the destination server to the originator unchanged. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format. \nWhen participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server, the intermediary server **SHOULD**: 1. Support the XML source format.",
"security" : {
"description" : "1. Communication security implemented by the intermediary server SHALL conform with the guidelines stated in [FHIR Security](https://www.hl7.org/fhir/security.html) for all exchanges covered in this IG. When using TLS: the inbound gateway intermediary SHALL hold the TLS certificate for the destinationâs public FHIR service base URL the certificates exchanged by the destination system, and any delegated intermediaries SHALL reflect their serversâ private URLs. \n1. Security tokens generated by the destination for use by the originator SHALL be forwarded by the intermediary server to the originating client. \n1. The intermediary server MAY implement the [HL7 / UDAP Security for Scalable Registration, Authentication, and Authorization FHIR Implementation Guide](http://hl7.org/fhir/us/udap-security/2021Sep). 1. For general security considerations refer to [FHIR Security and Privacy Considerations](https://www.hl7.org/fhir/secpriv-module.html)."
}
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.